Sponsoring data usage and usage of content provider web sites and applications

ABSTRACT

A device receives an identifier associated with a user device, and receives information associated with data usage by the user device. The device determines whether the data usage is sponsored by a sponsor based on the identifier and the information associated with the data usage. The sponsor sponsors data usage associated with particular content accessed by the user device. The device assigns charges for the data usage to an account associated with the user device when the data usage is not sponsored by the sponsor, or to an account associated with the sponsor when the data usage is sponsored by the sponsor.

BACKGROUND

A user may utilize a mobile device (e.g., a smart phone, a tabletcomputer, a laptop computer, etc.) to access and view content, such as,for example, a web site, a video, etc., provided by a content provider.The user may accrue data usage charges for accessing the content. Manyemployers permit employees to bring personally-owned mobile devices totheir workplace, and to use those mobile devices to access privilegedcompany information and applications. Such an arrangement may bereferred to as bring your own device (BYOD). The employers may manuallyreimburse the employees for data usage charges accrued at the workplaceif the employees submit paperwork (e.g., telephone bills) to theemployers.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of an overview of an example implementationdescribed herein;

FIG. 2 is a diagram of an example environment in which systems and/ormethods described herein may be implemented;

FIG. 3 is a diagram of example components of a device that maycorrespond to one or more of the devices of the environment depicted inFIG. 2;

FIG. 4 is a flow chart of an example process for creating andconfiguring a data usage sponsorship campaign for a sponsor;

FIG. 5A is a diagram of an example user interface that may be used inconnection with the example process shown in FIG. 4;

FIG. 5B is a diagram of an example data structure that may be used inconnection with the example process shown in FIG. 4;

FIG. 6 is a flow chart of an example process for sponsoring data usageand usage of content provider web sites and/or applications;

FIG. 7A-7D are diagrams of an example relating to the example processshown in FIG. 6; and

FIG. 8A-8E are diagrams of another example relating to the exampleprocess shown in FIG. 6.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description refers to the accompanying drawings.The same reference numbers in different drawings may identify the sameor similar elements.

FIG. 1 is a diagram of an overview of an example implementation 100described herein. As shown in FIG. 1, assume that an employee of acompany is associated with a first user device that receives content(e.g., provided by a content provider) from a content server. Further,assume that a non-employee of the company is associated with a seconduser device that also receives the content from the content server. Insome implementations, the content provided to the user devices mayinclude embedded code that causes the user devices to provide deviceidentifiers of the user devices to the content server (e.g., with thepermission of the users) and/or to an identity server. For example, theembedded code may cause the first user device to provide a first deviceidentifier (ID) to the content server, and may cause the second userdevice to provide a second device ID to the content server, as shown inFIG. 1.

As further shown, the content server may forward the first and seconddevice IDs to the identity server. As the first user device accesses andreceives the content, data usage may be accrued for the employee andinformation identifying the employee's data usage (e.g., contentaccessed, time periods when content accessed, etc.) may be provided tothe identity server. As the second user device accesses and receives thecontent, data usage may be accrued for the non-employee and informationidentifying the non-employee's data usage may be provided to theidentity server.

Assume that the employer, via a sponsor server, created a sponsorshipcampaign with the identity server. The sponsorship campaign may indicatethat the employer will sponsor data usage charges for the employee's useof the content received from the content server. The identity server mayreceive the device IDs, the information identifying the employee's datausage, and the information identifying the non-employee's data usage.Based on the second device ID, the identity server may determine thatthe non-employee's data usage is not covered by the sponsorshipcampaign, and may charge the non-employee's data usage to an accountassociated with the non-employee.

Based on the first device ID and the information identifying theemployee's data usage, the identity server may determine that theemployee's data usage, associated with the content, is covered by thesponsorship campaign. For example, the sponsorship campaign may coverthe employee's use of the content received from the content server, butnot the employee's use of the other content received from other sources.Based on this determination, the identity server may provide, to thesponsor server, information identifying data charges associated with theemployee's use of the content. As further shown in FIG. 1, the sponsorserver may pay the data charges for the employee's use of the content inaccordance with the sponsorship campaign. The identity server may chargethe employee's data usage, associated with the other content, to anaccount associated with the employee.

The systems and/or methods described herein may enable entities (e.g.,sponsors) to fully or partially sponsor a user's data usage and/orcharges associated with using one or more content providers' web pages,web sites, applications, content, etc. The user's data usage and/orcharges associated with using one or more content providers' web pages,web sites, applications, content, etc. may be automatically handled,without the user submitting paperwork for reimbursement. The systemsand/or methods may also enable the sponsors to define the sponsorshipbased on parameters, such as quantity of data used, time of day,specific users, content, portions or specific features of content, etc.

Content, as used herein, is to be broadly interpreted to include a website, a web page, an application, a video, audio, an image, text, asoftware download, and/or a combination of a web site, a web page, anapplication, a video, audio, an image, text, and/or a software download.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods described herein may be implemented. As illustrated,environment 200 may include a user device 210, a content server 220, anidentity server 230, a sponsor server 240, and a network 250.Devices/networks of environment 200 may interconnect via wiredconnections, wireless connections, or a combination of wired andwireless connections.

User device 210 may include a device that is capable of communicatingover network 250 with content server 220, identity server 230, and/orsponsor server 240. In some implementations, user device 210 may includea radiotelephone; a personal communications services (PCS) terminal thatmay combine, for example, a cellular radiotelephone with data processingand data communications capabilities; a smart phone; a personal digitalassistant (PDA) that can include a radiotelephone, a pager,Internet/intranet access, etc.; a laptop computer; a tablet computer; adesktop computer; a workstation computer; a personal computer, alandline telephone; a gaming device; or another type of computation andcommunication device.

Content server 220 may include one or more personal computers,workstation computers, server devices, or other types of computation andcommunication devices. In some implementations, content server 220 mayprovide content to user device 210 (e.g., via a web site and/or anapplication). In some implementations, the content may include embeddedcode that instructs user device 210 to provide an identifier (e.g., amobile directory number (MDN), a mobile equipment identifier (MEID), anInternet protocol (IP) address, etc.) of user device 210 to contentserver 220 (e.g., with the permission of the user) and/or identityserver 230 while user device 210 receives the content. In someimplementations, the embedded code may be provided by identity server230 to content server 220, and may enable content server 220 to supportdata usage sponsorship campaigns provided by one or more sponsors (e.g.,associated with sponsor servers 240). In some implementations, theembedded code may include an application, a code snippet, a script, awidget, etc. that may enable content server 220 to support the datausage sponsorship campaigns.

Identity server 230 may include one or more personal computers,workstation computers, server devices, or other types of computation andcommunication devices. In some implementations, identity server 230 maybe associated with a communication provider (e.g., an Internet serviceprovider, a telecommunications service provider, a television serviceprovider, etc.) of the user of user device 210. In some implementations,identity server 230 may identify the user of user device 210 based on anidentifier (e.g., a MDN, a MEID, an IP address, etc.) associated withuser device 210. In some implementations, identity server 230 mayprovide the embedded code to content server 220. The embedded code mayinstruct user device 210 to provide the identifier of user device 210 tocontent server 220 and/or identity server 230 while user device 210receives the content from content server 220.

Sponsor server 240 may include one or more personal computers,workstation computers, server devices, or other types of computation andcommunication devices. In some implementations, sponsor server 240 maybe associated with an entity (e.g., a company, a government agency, auniversity, a sports team, etc.) that sponsors data usage for users ofuser devices 210. For example, sponsor server 240 may be associated witha company that sponsors data usage of the company's employees; a companythat sponsors data usage of spectators at a sporting event (e.g., afootball game, a baseball game, etc.); a hotel that sponsors data usageof guests that stay at the hotel; etc. In some implementations, sponsorserver 240 may also provide content to user device 210 in addition to orinstead of content server 220. For example, if sponsor server 240 isassociated with a company, sponsor server 240 may provide and/or sponsorcontent (e.g., a company intranet, company documents, etc.) that may beaccessed by an employee (e.g., via user device 210).

Network 250 may include a network, such as a local area network (LAN), awide area network (WAN), a metropolitan area network (MAN), a telephonenetwork, such as the Public Switched Telephone Network (PSTN) or acellular network, an intranet, the Internet, a fiber optic network, or acombination of networks.

The number of devices and/or networks shown in FIG. 2 is provided as anexample. In practice, there may be additional devices and/or networks,fewer devices and/or networks, different devices and/or networks, ordifferently arranged devices and/or networks than those shown in FIG. 2.Furthermore, two or more devices shown in FIG. 2 may be implementedwithin a single device, or a single device shown in FIG. 2 may beimplemented as multiple, distributed devices. Additionally, one or moreof the devices of environment 200 may perform one or more functionsdescribed as being performed by another one or more devices ofenvironment 200.

FIG. 3 is a diagram of example components of a device 300 that maycorrespond to one or more of the devices of environment 200. In someimplementations, one or more of the devices of environment 200 mayinclude one or more devices 300 or one or more components of device 300.As shown in FIG. 3, device 300 may include a bus 310, a processor 320, amemory 330, an input component 340, an output component 350, and acommunication interface 360.

Bus 310 may include a path that permits communication among thecomponents of device 300. Processor 320 may include a processor (e.g., acentral processing unit, a graphics processing unit, an acceleratedprocessing unit, etc.), a microprocessor, and/or any processingcomponent (e.g., a field-programmable gate array (FPGA), anapplication-specific integrated circuit (ASIC), etc.) that interpretsand/or executes instructions, and/or that is designed to implement aparticular function. In some implementations, processor 320 may includemultiple processor cores for parallel computing. Memory 330 may includea random access memory (RAM), a read only memory (ROM), and/or anothertype of dynamic or static storage component (e.g., a flash, magnetic, oroptical memory) that stores information and/or instructions for use byprocessor 320.

Input component 340 may include a component that permits a user to inputinformation to device 300 (e.g., a touch screen display, a keyboard, akeypad, a mouse, a button, a switch, etc.). Output component 350 mayinclude a component that outputs information from device 300 (e.g., adisplay, a speaker, one or more light-emitting diodes (LEDs), etc.).

Communication interface 360 may include a transceiver-like component,such as a transceiver and/or a separate receiver and transmitter, whichenables device 300 to communicate with other devices, such as via awired connection, a wireless connection, or a combination of wired andwireless connections. For example, communication interface 360 mayinclude an Ethernet interface, an optical interface, a coaxialinterface, an infrared interface, a radio frequency (RF) interface, auniversal serial bus (USB) interface, a high-definition multimediainterface (HDMI), or the like.

Device 300 may perform various operations described herein. Device 300may perform these operations in response to processor 320 executingsoftware instructions included in a computer-readable medium, such asmemory 330. A computer-readable medium is defined as a non-transitorymemory device. A memory device includes memory space within a singlephysical storage device or memory space spread across multiple physicalstorage devices.

Software instructions may be read into memory 330 from anothercomputer-readable medium or from another device via communicationinterface 360. When executed, software instructions stored in memory 330may cause processor 320 to perform one or more processes describedherein. Additionally, or alternatively, hardwired circuitry may be usedin place of or in combination with software instructions to perform oneor more processes described herein. Thus, implementations describedherein are not limited to any specific combination of hardware circuitryand software.

The number of components shown in FIG. 3 is provided as an example. Inpractice, device 300 may include additional components, fewercomponents, different components, or differently arranged componentsthan those shown in FIG. 3. Additionally, or alternatively, one or morecomponents of device 300 may perform one or more functions described asbeing performed by another one or more components of device 300.

FIG. 4 is a flow chart of an example process 400 for creating andconfiguring a data usage sponsorship campaign for a sponsor. In someimplementations, one or more process blocks of FIG. 4 may be performedby identity server 230. In some implementations, one or more processblocks of FIG. 4 may be performed by another device or a group ofdevices separate from or including identity server 230.

As shown in FIG. 4, process 400 may include receiving a request tocreate a data usage sponsorship campaign from a sponsor server (block410). For example, a sponsor (e.g., a company, a hotel, etc.) may causesponsor server 240 to provide a request to create a data usagesponsorship campaign to identity server 230, and identity server 230 mayreceive the request to create the data usage sponsorship campaign. Insome implementations, the data usage sponsorship campaign may include acampaign where the sponsor pays for data usage by user device 210 basedon a relationship between the sponsor and the user of user device. Forexample, the sponsor may pay for data usage when user device 210accesses all content provided by content server 220, particular contentprovided by content server 220, any content, other content provided byother content providers, etc.

In some implementations, the sponsor may cause sponsor server 240 toaccess identity server 230 via, for example, a user interface (such as abrowser) or in another manner. The sponsor may then select, usingsponsor server 240, information regarding the data usage sponsorshipcampaign from the user interface to cause content server 220 to providethe request to create the data usage sponsorship campaign to identityserver 230. In some implementations, identity server 230 may offerinformation for creating the data usage sponsorship campaign to sponsorserver 240 without sponsor server 240 providing the request.

As further shown in FIG. 4, process 400 may include providing a userinterface requesting campaign preferences to the sponsor server (block420). For example, identity server 230 may provide a user interface,requesting data usage sponsorship campaign preferences, to sponsorserver 240 based on the request. In some implementations, the userinterface may request a variety of information associated with thecampaign preferences. For example, the user interface may request a nameof the sponsor, contact information for the sponsor, an address of thesponsor, a telephone number for the sponsor, account information of thesponsor (e.g., billing information for the sponsor, a tax identificationof the sponsor, etc.), etc. In some implementations, identity server 230may previously obtain the aforementioned information if the sponsorestablishes an account with identity server 230.

In some implementations, the user interface may request identifiers ofuser devices 210 to associate with the campaign. For example, if thesponsor is an employer creating a campaign for the employer's employees(e.g., sponsoring all data usage by the employees), the employer mayprovide identifiers of user devices 210 associated with the employeesvia the user interface. In some implementations, the user interface mayrequest a date range for the campaign. For example, if the sponsor is ahotel creating a campaign for a hotel guest (e.g., sponsoring data usageby the hotel guest), the hotel may provide a date range associated withwhen the hotel guest is staying at the hotel (e.g., from Dec. 1, 2013 toDec. 4, 2013) via the user interface.

In some implementations, the user interface may request content toassociate with the campaign. For example, if the sponsor is an employercreating a campaign for an employee of the employer, the employer mayindicate, via the user interface, that the employer is sponsoring alldata usage of the employee, data usage of particular content by theemployee, data usage of only the employer's content, etc. In someimplementations, the user interface may request a location range for thecampaign. For example, if the sponsor is a bank creating a campaign forfans attending a football game at a stadium, the bank may indicate, viathe user interface, that the bank is sponsoring data usage for the fansthat are physically or geographically located within the stadium duringthe football game.

In some implementations, the user interface may request a time range forthe campaign. For example, if the sponsor is a restaurant creating acampaign for the patrons of the restaurant when the restaurant is open,the restaurant may indicate, via the user interface, that the restaurantis sponsoring data usage for the patrons that are physically orgeographically located within the restaurant between the hours of 9:00AM and 3:00 PM (e.g., when the restaurant is open). In someimplementations, the user interface may request a data usage thresholdfor the campaign. For example, if the sponsor is an employer creating acampaign for an employee of the employer, the employer may indicate, viathe user interface, that the employer is sponsoring all data usage ofthe employee up to a particular data usage threshold (e.g., less than orequal to a particular number of bits, gigabits (Gbits), etc.).

In some implementations, a type of the account, of the sponsor, maydetermine the quantity of campaign preferences that the sponsor is ableto identify via the user interface. For example, the user interface mayenable the content provider to identify only a portion of the abovepreferences or identify additional preferences based on the type of theaccount with which the sponsor is associated.

As further shown in FIG. 4, process 400 may include receiving thecampaign preferences via the user interface (block 430). For example,the sponsor may cause sponsor server 240 to provide, to identity server230, information identifying the one or more preferences relating to thedata usage sponsorship campaign and provided via the user interface.Identity server 230 may receive the one or more preferences relating tothe data usage sponsorship campaign.

As further shown in FIG. 4, process 400 may include generatingconfiguration information for the campaign based on the preferences(block 440). For example, identity server 230 may generate configurationinformation based on the one or more preferences relating to the datausage sponsorship campaign. In some implementations, the configurationinformation may include information that indicates the name of thesponsor, the contact information for the sponsor, the address of thesponsor, the telephone number for the sponsor, the account informationof the sponsor, etc.

In some implementations, the configuration information may includeinformation that provides the identifiers of user devices 210 associatedwith the data usage sponsorship campaign. In some implementations, theconfiguration information may include information that indicates thedate range for the data usage sponsorship campaign. In someimplementations, the configuration information may include informationthat indicates content to associate with the data usage sponsorshipcampaign. In some implementations, the configuration information mayinclude information that indicates the location range for the data usagesponsorship campaign. In some implementations, the configurationinformation may include information that indicates the time range forthe data usage sponsorship campaign. In some implementations, theconfiguration information may include information that indicates thedata usage threshold for the data usage sponsorship campaign.

As further shown in FIG. 4, process 400 may include storing theconfiguration information and configuring the campaign based on theconfiguration information (block 450). For example, identity server 230may store all or a portion of the configuration information generated byidentity server 230 (e.g., in a data structure). In someimplementations, identity server 230 may configure the data usagesponsorship campaign based on all or a portion of the storedconfiguration information.

In some implementations, sponsor server 240 may provide updates, to theone or more preferences relating to the data usage sponsorship campaign,to identity server 230 based on execution of the data usage sponsorshipcampaign. For example, sponsor server 240 may provide updates to the oneor more preferences when user devices 210 associated with the campaignneed to be changed (e.g., a hotel guest leaves the hotel, an employeeleaves a company, a new employee joins a company, etc.). In anotherexample, sponsor server 240 may provide updates to the one or morepreferences when other conditions associated with the campaign change(e.g., an employer may want to expand the content covered by thecampaign, a restaurant may want to restrict data usage to a particularthreshold, etc.). Identity server 230 may generate updates to theconfiguration information based on the updated preferences, and maystore the updates to the configuration information. In someimplementations, sponsor server 240 may provide the updates periodicallybased on a preference of the sponsor and/or based on a time frequencydetermined by sponsor server 240. In some implementations, sponsorserver 240 may determine whether to provide the updates based on thetype of the account associated with the sponsor.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4. Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel.

FIG. 5A is a diagram 500 of an example user interface 510 that may beused in connection with example process 400 shown in FIG. 4. In someimplementations, user interface 510 may be provided by identity server230 to sponsor server 240 to enable a sponsor to identify information(e.g., preferences) that may be used to configure a data usagesponsorship campaign.

As shown in FIG. 5A, user interface 510 may allow the sponsor toconfigure different features of the data usage sponsorship campaign. Forexample, the sponsor may identify one or more preferences for initiationof the data usage sponsorship campaign. In some implementations, thesponsor may indicate device identifiers of user devices 210 to associatewith the data usage sponsorship campaign via user interface 510. Forexample, as shown in FIG. 5A, the sponsor may identify two MDNs (e.g.,111-111-1111 and 222-222-2222) and two IP addresses (e.g., 172.16.254.1and 164.32.254.2) as device identifiers of user devices 210 to associatewith the data usage sponsorship campaign. In another example, thesponsor may upload a spreadsheet of device identifiers to associate withthe data usage sponsorship campaign. In some implementations, thesponsor may indicate a date range for the data usage sponsorshipcampaign via user interface 510. For example, as shown in FIG. 5A, thesponsor may indicate a start date of Dec. 30, 2013 and an end date ofJan. 15, 2014 for the date range of the data usage sponsorship campaign.

In some implementations, the sponsor may indicate content to associatewith the data usage sponsorship campaign via user interface 510. Forexample, as shown in FIG. 5A, the sponsor may indicate that the sponsoris sponsoring all data usage or particular content for the data usagesponsorship campaign. In some implementations, the sponsor may indicatea location range for the data usage sponsorship campaign via userinterface 510. For example, as shown in FIG. 5A, the sponsor mayindicate that the data usage sponsorship campaign covers designated userdevices 210 that are physically or geographically located within twomiles of a particular address.

In some implementations, the sponsor may indicate a time range for thedata usage sponsorship campaign via user interface 510. For example, asshown in FIG. 5A, the sponsor may indicate that the sponsor issponsoring data usage by designated user devices 210 between the hoursof 9:00 AM and 5:00 PM. In some implementations, the sponsor mayindicate a data usage threshold for the data usage sponsorship campaignvia user interface 510. For example, as shown in FIG. 5A, the sponsormay indicate that the data usage sponsorship campaign covers data usageby designated user devices 210 up to a particular data usage threshold(e.g., less than a particular number of Gbits).

Once the sponsor has identified the preferences, user interface 510 mayallow the sponsor to select a “Submit” option to store the preferencesand/or submit the preferences to identity server 230. Identity server230 may then generate configuration information based on thepreferences.

As further shown in FIG. 5A, user interface 510 may also allow thesponsor to select a “Back” option to cause identity server 230 toprovide information regarding the data usage sponsorship campaign. Asalso shown in FIG. 5A, user interface 510 may also allow the sponsor toselect a “More Configuration” option to enable the sponsor to identifyadditional information that may be used to configure the data usagesponsorship campaign.

The number of elements of user interface 510 shown in FIG. 5A isprovided for explanatory purposes. In practice, user interface 510 mayinclude additional elements, fewer elements, different elements, ordifferently arranged elements than those shown in FIG. 5A.

FIG. 5B is a diagram 500 of an example data structure 520 that may beused in connection with example process 400 shown in FIG. 4. In someimplementations, data structure 520 may be created, maintained, and/orstored by identity server 230, and may be used to implement a data usagesponsorship campaign. In some implementations, data structure 520 may becreated, maintained, and/or stored by another device or a group ofdevices separate from or including identity server 230. In someimplementations, data structure 520 may include a database, a table, alist, an array, etc.

As shown in FIG. 5B, data structure 520 may include a table with acampaign identifier (ID) field, a sponsor field, a sponsor accountfield, a device IDs field, a date range field, a content field, alocation field, a time field, a threshold field, and various entriesassociated with the fields. In some implementations, data structure 520may include a different type of data structure, different fields,additional fields, and/or differently arranged fields.

The campaign ID field may include identifiers assigned to different datausage sponsorship campaigns by identity server 230. In someimplementations, a sponsor may be associated with one or more campaignIDs that correspond to one or more data usage sponsorship campaignscreated by the sponsor. For example, as shown in FIG. 5B, a company maybe associated with a first campaign ID (e.g., “123”), a hotel may beassociated with a second campaign ID (e.g., “456”), etc.

The sponsor field may include information associated with a sponsor of adata usage sponsorship campaign identified in campaign ID field. In someimplementations, the information associated with the sponsor may includea name of the sponsor, a physical address of the sponsor, contactinformation of the sponsor, billing information of the sponsor, etc. Forexample, as shown in FIG. 5B, the company may be associated with thefirst campaign ID, the hotel may be associated with the second campaignID, a sports team may be associated with the third campaign ID, etc.

The sponsor account field may include an account associated with thesponsor identified in the sponsor field. In some implementations, theaccount may include a billing account, of the sponsor, to which tocharge the sponsor for data usage associated with a data usagesponsorship campaign identified in the campaign ID field. For example,as shown in FIG. 5B, the company may include a billing account (e.g.,“123456”) associated with the first campaign ID, the hotel may include abilling account (e.g., “789101”) associated with the second campaign ID,etc.

The device IDs field may include one or more device identifiers of userdevices 210 associated with a data usage sponsorship campaign identifiedin campaign ID field. In some implementations, the device identifiersmay include MDNs, MEIDs, IP addresses, telephone numbers, etc. of userdevices 210 associated with the data usage sponsorship campaign. Forexample, as shown in FIG. 5B, a MDN (e.g., “xxx-xxx-xxxx”) and an IPaddress (e.g., “172.16.234.1”) may be associated with the first campaignID, a telephone number (e.g., “yyy-yyy-yyyy”) may be associated with thesecond campaign ID, etc.

The date range field may include a date range associated with a datausage sponsorship campaign identified in the campaign ID field. In someimplementations, the date range may define a date when a data usagesponsorship campaign, identified in the campaign ID field, is effective.For example, as shown in FIG. 5B, the data usage sponsorship campaignassociated with the first campaign ID may be effective from Jan. 1, 2014to Jan. 2, 2014, the data usage sponsorship campaign associated with thesecond campaign ID may be effective from Dec. 15, 2013 to Jan. 1, 2014,etc.

The content field may include information associated with content thatis to be sponsored by a data usage sponsorship campaign identified inthe campaign ID field. In some implementations, the informationassociated with the content may include one or more web site addresses(e.g., uniform resource locators (URLs)), web page addresses,information indicating all data usage, etc. For example, as shown inFIG. 5B, the data usage sponsorship campaign associated with the firstcampaign ID may cover a single URL (e.g., “URL1”), the data usagesponsorship campaign associated with the second campaign ID may coverall data usage, etc.

The location field may include information identifying a locationassociated with a data usage sponsorship campaign identified in thecampaign ID field. In some implementations, the location field mayinclude information indicating that the data usage sponsorship campaign,identified in the campaign ID field, covers designated user devices 210that are physically located within a particular distance of a particularaddress. For example, as shown in FIG. 5B, the data usage sponsorshipcampaign associated with the first campaign ID may not be limited to aparticular location, the data usage sponsorship campaign associated withthe second campaign ID may be limited to data usage within one mile of aparticular address (e.g., an address of the hotel), etc.

The time field may include information identifying a time rangeassociated with a data usage sponsorship campaign identified in thecampaign ID field. In some implementations, the time field may includeinformation indicating that the data usage sponsorship campaign,identified in the campaign ID field, covers data usage by designateduser devices 210 between a particular time period. For example, as shownin FIG. 5B, the data usage sponsorship campaigns associated with thefirst campaign ID and the second campaign ID may not be limited to aparticular time range, the data usage sponsorship campaign associatedwith the third campaign ID may be limited to data usage during a time agame is being played, etc.

The threshold field may include information identifying a data usagethreshold associated with a data usage sponsorship campaign identifiedin the campaign ID field. In some implementations, the threshold fieldmay include information indicating that the data usage sponsorshipcampaign, identified in the campaign ID field, covers data usage bydesignated user devices 210 up to a particular data usage threshold. Forexample, as shown in FIG. 5B, the data usage sponsorship campaignsassociated with the first campaign ID and the second campaign ID may notbe limited to a particular data usage threshold, the data usagesponsorship campaign associated with the third campaign ID may belimited to a data usage threshold of less than a particular amount(e.g., “100 Gb”), etc.

FIG. 6 is a flow chart of an example process 600 for sponsoring datausage and usage of content provider web sites and/or applications. Insome implementations, one or more process blocks of FIG. 6 may beperformed by identity server 230. In some implementations, one or moreprocess blocks of FIG. 6 may be performed by another device or a groupof devices separate from or including identity server 230.

As shown in FIG. 6, process 600 may include receiving an identifier,associated with a user device, from a content server or from the userdevice (block 610). For example, a user may utilize user device 210 toaccess content provided by content server 220. In some implementations,user device 210 may access a web site, a web page, an application, etc.that includes content provided by content server 220, and may displaythe content to the user. For example, the user may provide, to userdevice 210, an address (e.g., URL) associated with a web page providedby content server 220, and user device 210 may access the content viathe web page and based on the address. In some implementations, thecontent may include embedded code that causes user device to provide adevice identifier (e.g., a MDN, a MEID, an IP address, etc.) of userdevice 210 to content server 220 (e.g., with the permission of the user)and/or to identity server 230. In some implementations, the deviceidentifier may be encrypted so that content server 220 may not be ableto determine the device identifier.

If user device 210 provides the device identifier to content server 220,content server 220 may forward the device identifier to identity server230, along with information associated with the content. In someimplementations, if the device identifier is encrypted, identity server230 may decrypt the device identifier (e.g., based on sharing encryptionkeys with user device 210). In some implementations, user device 210 mayprovide the device identifier to identity server 230 based on userdevice 210 utilizing a service (e.g., a telecommunications service, anInternet service, etc.) associated with identity server 230. Identityserver 230 may receive the device identifier of user device 210 fromcontent server 220 and/or from user device 210.

As further shown in FIG. 6, process 600 may include receivinginformation associated with data usage by the user device (block 620).For example, as user device 210 accesses the content from content server220, data usage may be accrued for user device 210. In someimplementations, user device 210 may access other content from othersources, and data usage may be accrued as user device 210 accesses theother content. In some implementations, user device 210 may generateinformation associated with the data usage, such as, for example,information identifying an amount of data usage by user device 210,information identifying the content accessed by user device 210,information identifying a date(s) when the content is accessed by userdevice 210, information identifying a location(s) of user device 210when the content is accessed by user device 210, information identifyinga time period(s) when the content is accessed by user device 210, etc.

In some implementations, user device 210 may provide the informationassociated with the data usage to identity server 230, and identityserver 230 may receive the information associated with the data usage.In some implementations, content server 220 may generate the informationassociated with the data usage of user device 210 (e.g., since contentserver 220 may host sponsored content). In such implementations, contentserver 220 may provide the information associated with the data usage toidentity server 230, and identity server 230 may receive the informationassociated with the data usage. In some implementations, identity server230 may store the information associated with the data usage of userdevice 210 in storage associated with identity server 230 (e.g., inmemory 330, FIG. 3).

As further shown in FIG. 6, process 600 may include determining whetherthe data usage is sponsored based on the identifier and the informationassociated with the data usage (block 630). For example, identity server230 may determine whether the data usage of user device 210 issponsored, by a sponsor, based on the device identifier of user device210 and based on the information associated with the data usage. In someimplementations, identity server 230 may include or be associated with adata structure (e.g., data structure 520) that includes informationassociated with data usage sponsorship campaigns. For example, the datastructure may include IDs associated with the data usage sponsorshipcampaigns; sponsor information associated with the data usagesponsorship campaigns; device identifiers (e.g., MDNs, MEIDs, etc.)associated with the data usage sponsorship campaigns; and/or otherinformation associated with the data usage sponsorship campaigns (e.g.,date ranges, location ranges, etc.). Identity server 230 may compare thedevice identifier of user device 210 with the device identifiersprovided in the data structure, and the information associated with thedata usage of user device 210 with the other information provided in thedata structure, in order to determine whether the data usage of userdevice 210 is sponsored.

In some implementations, if the device identifier of user device 210matches a particular device identifier in the data structure, identityserver 230 may identify a particular data usage sponsorship campaignassociated with the particular device identifier. Identity server 230may then compare the information associated with the data usage of userdevice 210 with the other information, associated with the particularcampaign and provided in data structure 520, in order to determinewhether the data usage of user device 210 meets the requirements of theother information.

As further shown in FIG. 6, if the data usage is not sponsored (block630—NO), process 600 may include assigning charges for the data usage toan account associated with the user device (block 640). For example, ifidentity server 230 determines that the data usage of user device 210 isnot sponsored, identity server 230 may assign charges for the data usageof user device 210 to an account associated with user device 210. Insome implementations, identity server 230 may determine that the datausage of user device 210 is not sponsored when the device identifier ofuser device 210 does not match a device identifier provided in datastructure 520. In some implementations, identity server 230 maydetermine that the data usage of user device 210 is not sponsored whenthe device identifier of user device 210 matches a device identifierprovided in data structure 520, but the data usage of user device 210does not meet one or more of the requirements of the other informationprovided in data structure 520. For example, assume that the deviceidentifier of user device 210 is associated with a particular data usagesponsorship campaign, provided in data structure 520. However, assumethat the data usage of user device 210 occurs during a date not within adate range associated with the particular data usage sponsorshipcampaign. In such an example, identity server 230 may determine that thedata usage of user device 210 is not sponsored because the data usage ofuser device 210 does not meet the date range requirement of thecampaign.

In some implementations, if identity server 230 determines that the datausage of user device 210 is not sponsored, identity server 230 mayassign charges for the data usage of user device 210 to an accountassociated with user device 210. For example, the user of user device210 may have established an account with identity server 230 for aservice (e.g., a telecommunications service, an Internet service, atelevision service, etc.) provided by identity server 230 to user device210. In such an example, identity server 230 may assign the charges forthe data usage of user device 210 to the user's account. In someimplementations, identity server 230 may generate a bill for the user'saccount, and the entity associated with identity server 230 may providethe bill to the user.

As further shown in FIG. 6, if the data usage is sponsored (block630—YES), process 600 may include determining a sponsor of the datausage (block 650). For example, if identity server 230 determines thatthe data usage of user device 210 is sponsored, identity server 230 maydetermine a sponsor of the data usage of user device 210. In someimplementations, identity server 230 may determine that the data usageof user device 210 is sponsored when the device identifier of userdevice 210 matches a device identifier provided in data structure 520,and the data usage of user device 210 meets the requirements of theother information, associated with the matching device identifier,provided in data structure 520. For example, assume that the deviceidentifier of user device 210 is associated with a particular data usagesponsorship campaign, provided in data structure 520. Further, assumethat the data usage of user device 210 occurs during a date within adate range associated with the particular data usage sponsorshipcampaign, and at a location within a location range associated with theparticular data usage sponsorship campaign. In such an example, identityserver 230 may determine that the data usage of user device 210 issponsored because the data usage of user device 210 meets the date rangerequirement and the location range requirement of the campaign.

In some implementations, if identity server 230 determines that the datausage of user device 210 is sponsored, identity server 230 may identifya sponsor associated with the data usage sponsorship campaign. Forexample, identity server 230 may identify, in data structure 520, aparticular data usage sponsorship campaign associated with the deviceidentifier of user device 210, and may further identify, in datastructure 520, a particular sponsor based on the particular data usagesponsorship campaign.

As further shown in FIG. 6, process 600 may include assigning thecharges for the data usage to an account associated with the sponsor(block 660). For example, if identity server 230 determines that thedata usage of user device 210 is sponsored by a sponsor, identity server230 may assign charges for the data usage of user device 210 to anaccount associated with the sponsor. In some implementations, ifidentity server 230 determines that the data usage of user device 210 issponsored, identity server 230 may assign charges for the data usage ofuser device 210 to an account associated with sponsor server 240. Forexample, a sponsor of sponsor server 240 may have established an accountwith identity server 230 for sponsoring data usage by one or more userdevices 210. In such an example, identity server 230 may assign thecharges for the data usage of user device 210 to the sponsor's account.In some implementations, identity server 230 may generate a bill for thesponsor's account, and the entity associated with identity server 230may provide the bill to the sponsor.

In some implementations, content server 220 may receive a campaign IDfrom identity server 230. In such implementations, the campaign ID maybe associated with a data usage sponsorship campaign that sponsors datausage by user devices 210 determined by content server 220. Contentserver 220 may determine a particular user device 210 to which toprovide the campaign ID, and may provide the campaign ID to theparticular user device 210 via content generated by content server 220.In some implementations, content server 220 may authenticate theparticular user device 210 before providing the campaign ID to theparticular user device 210. As the particular user device 210 accessesthe content from content server 220, data usage may be accrued for theparticular user device 210. In some implementations, the particular userdevice 210 may generate information associated with the data usage, suchas, for example, information identifying an amount of data usage by theparticular user device 210, information identifying the content accessedby the particular user device 210, information identifying a location(s)of the particular user device 210 when the content is accessed by theparticular user device 210, the campaign ID, etc. In suchimplementations, identity server 230 may utilize the campaign ID as abasis for sponsoring the data usage of the content by the particularuser device 210.

Although FIG. 6 shows example blocks of process 600, in someimplementations, process 600 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 6. Additionally, or alternatively, two or more of theblocks of process 600 may be performed in parallel.

FIGS. 7A-7D are diagrams of an example 700 relating to example process600 shown in FIG. 6. In example 700, assume that a sponsor (e.g., acompany) is associated with sponsor server 220, as shown in FIG. 7A.Further, assume that the company utilizes sponsor server 240 to sponsordata usage by the company's employees for particular content, asindicated by reference number 705. For example, the company may utilizesponsor server 240 to access a user interface (e.g., user interface 510,FIG. 5A), provided by identity server 230, that enables the company tocreate a data usage sponsorship campaign for the employees. As shown inFIG. 7A, identity server 230 may store the data usage sponsorshipcampaign in data structure 520. The data usage sponsorship campaign mayinclude particular device IDs (e.g., “xxx-xxx-xxxx” and “172.16.234.1”),a date range (e.g., Jan. 1, 2014 to Jan. 2, 2014), and particularcontent (e.g., content received from content server 220). As furthershown in FIG. 7A, identity server 230 may assign a sponsorship campaignID 710 (e.g., “456”) to the data usage sponsorship campaign, and mayprovide sponsorship campaign ID 710 to sponsor server 240.

Now assume that an employee of the company is associated with a userdevice 210 (e.g., a smart phone 210), as shown in FIG. 7B. Further,assume that the employee utilizes smart phone 210 to access content 715provided by content server 220. For example, the employee may access aweb site 720 of content server 220, and smart phone 210 may display website 720 to the employee. As further shown in FIG. 7B, web site 720 mayinclude embedded code 725 that causes smart phone 210 to provide anidentifier (ID) 730 (e.g., “xxx-xxx-xxxx”) of smart phone 210 to contentserver 220 (e.g., with the employee's permission and/or in an encryptedformat).

As shown in FIG. 7C, content server 220 may forward identifier 730 ofsmart phone 210 to identity server 230, and identity server 230 maydecrypt identifier 730 if identifier 730 is encrypted. While smart phone210 accesses web site 720, smart phone 210 may accrue data usage, andinformation 735 associated with the data usage of web site 720 may beprovided to identity server 230, as further shown in FIG. 7C. In someimplementations, information 735 may include an address of web site 720,date and time information associated with the access of web site 720,location information of smart phone 210, etc. In example 700, assumethat the employee accesses web site 720 on Jan. 1, 2014. Identity server230 may compare identifier 730 and information 735 with informationprovided in data structure 520 in order to determine whether smartphone's 210 data usage for accessing web site 720 is sponsored. Asfurther shown in FIG. 7C, identity server 230 may determine that smartphone's 210 data usage for accessing web site 720 is sponsored sinceidentifier 730 and information 735 match information provided in datastructure 520, as indicated by reference number 740. For example,identifier 730 (e.g., “xxx-xxx-xxxx”) may match a device identifierassociated with campaign ID 456, the date range associated with campaignID 456 may be satisfied, and the content requirement associated withcampaign ID 456 may be satisfied.

Based on this determination, identity server 230 may identify thecompany as the sponsor associated with campaign ID 456, and may generatedata charges 745 for the employee's access of web site 720, as shown inFIG. 7D. As further shown in FIG. 7D, identity server 230 may providedata charges 745 for the employee's access of web site 720 to sponsorserver 240 (e.g., to the company). In some implementations, the companymay instruct sponsor server 240 to generate an electronic payment 750for data charges 745, and to provide electronic payment 750 to an entityassociated with identity server 230. In some implementations, thecompany may generate a manual payment 755 (e.g., a check) for datacharges 745, and may provide manual payment 755 (e.g., via mail) to anentity associated with identity server 230.

If the employee accesses other content not sponsored by the company,identity server 230 may generate other data charges for the employee'saccess of the other content, and may provide the other data charges tothe employee. In some implementations, the employee may instruct smartphone 210 to generate an electronic payment for the other data charges,and to provide the electronic payment to identity server 230. In someimplementations, the employee may generate a manual payment (e.g., acheck) for the other data charges, and may provide the manual payment(e.g., via mail) to an entity associated with identity server 230.

As indicated above, FIGS. 7A-7D are provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIGS. 7A-7D. In some implementations, the various operationsdescribed in connection with FIGS. 7A-7D may be performed automaticallyor at the request of the user.

FIGS. 8A-8E are diagrams of another example 800 relating to exampleprocess 600 shown in FIG. 6. In example 800, assume that a sponsor(e.g., a hotel) is associated with sponsor server 220, and that a guestof the hotel is associated with a user device 210 (e.g., a smart phone210), as shown in FIG. 8A. As further shown, the guest may check in 805to the hotel, and an employee of the hotel may inform the guest that thehotel sponsors all data usage by the guest while the guest stays at thehotel. Accordingly, the guest may provide an identifier 810 (e.g.,“yyy-yyy-yyyy”) of smart phone 210 to the employee, and the employee mayinput identifier 810 to sponsor server 240.

Further, assume that the hotel utilizes sponsor server 240 to sponsorall data usage by the hotel's guests, as indicated by reference number815 in FIG. 8B. For example, the hotel may utilize sponsor server 240 toaccess a user interface (e.g., user interface 510, FIG. 5A), provided byidentity server 230, that enables the hotel to create a data usagesponsorship campaign for the guests. As shown in FIG. 8B, identityserver 230 may store the data usage sponsorship campaign in datastructure 520. The data usage sponsorship campaign may include aparticular device ID (e.g., “yyy-yyy-yyyy”), a particular date range(e.g., Dec. 15, 2013 to Jan. 1, 2014), and particular content (e.g., alldata usage). In some implementations, the hotel's data usage sponsorshipcampaign may include additional device IDs and/or date ranges associatedwith other guests of the hotel. As further shown in FIG. 8B, identityserver 230 may assign a sponsorship campaign ID 820 (e.g., “123”) to thedata usage sponsorship campaign, and may provide sponsorship campaign ID820 to sponsor server 240.

Now assume that the guest utilizes smart phone 210 to access content 825provided by a first content server 220-1, and to access content 830provided by a second content server 220-2, as shown in FIG. 8C. Forexample, the guest may access a web site 835 of the first content server220-1, and smart phone 210 may display web site 835 to the guest. Insome implementations, the guest may also utilize smart phone 210 toaccess other content provided by other content providers.

As shown in FIG. 8D, smart phone 210 may forward identifier 810 of smartphone 210 to identity server 230, when smart phone 210 is accessingcontent 825 and/or content 830. While smart phone 210 accesses content825 and/or content 830, smart phone 210 may accrue data usage, andinformation 840 associated with all data usage by smart phone 210 (e.g.,the data usage for accessing content 825 and/or content 830) may beprovided to identity server 230, as further shown in FIG. 8D. In someimplementations, information 840 may include information associated withcontent 825 and/or content 830, date and time information associatedwith the access of content 825 and/or content 830, location informationof smart phone 210, etc.

In example 800, assume that the guest accesses content 825 and/orcontent 830 on Dec. 18, 2013. Identity server 230 may compare identifier810 and information 840 with information provided in data structure 520in order to determine whether smart phone's 210 data usage for accessingcontent 825 and/or content 830 is sponsored. Identity server 230 maydetermine that smart phone's 210 data usage, for accessing content 825and/or content 830, is sponsored since identifier 810 and information840 match information provided in data structure 520, as indicated byreference number 845 in FIG. 8D. For example, identifier 810 (e.g.,“yyy-yyy-yyyy”) may match a device identifier associated with campaignID 123, the date range associated with campaign ID 123 may be satisfied,and the content requirement associated with campaign ID 123 may besatisfied.

Based on this determination, identity server 230 may identify the hotelas the sponsor associated with campaign ID 123, and may generate datacharges 850 for the guest's data usage, as shown in FIG. 8E. As furthershown in FIG. 8E, identity server 230 may provide data charges 850 forthe guest's data usage to sponsor server 240 (e.g., to the hotel). Insome implementations, the hotel may instruct sponsor server 240 togenerate an electronic payment 855 for data charges 850, and to provideelectronic payment 855 to an entity associated with identity server 230.In some implementations, the hotel may generate a manual payment 860(e.g., a check) for data charges 850, and may provide manual payment 860(e.g., via mail) to an entity associated with identity server 230.

As indicated above, FIGS. 8A-8E are provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIGS. 8A-8E. In some implementations, the various operationsdescribed in connection with FIGS. 8A-8E may be performed automaticallyor at the request of the user.

To the extent the aforementioned implementations collect, store, oremploy personal information provided by individuals, it should beunderstood that such information shall be used in accordance with allapplicable laws concerning protection of personal information.Additionally, the collection, storage, and use of such information maybe subject to consent of the individual to such activity, for example,through “opt-in” or “opt-out” processes as may be appropriate for thesituation and type of information. Storage and use of personalinformation may be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or may be acquired from practice of theimplementations.

A component is intended to be broadly construed as hardware, firmware,or a combination of hardware and software.

It will be apparent that systems and/or methods, as described herein,may be implemented in many different forms of software, firmware, andhardware in the implementations illustrated in the figures. The actualsoftware code or specialized control hardware used to implement thesesystems and/or methods is not limiting of the implementations. Thus, theoperation and behavior of the systems and/or methods were describedwithout reference to the specific software code—it being understood thatsoftware and control hardware can be designed to implement the systemsand/or methods based on the description herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items,and may be used interchangeably with “one or more.” Where only one itemis intended, the term “one” or similar language is used. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A method comprising: receiving, by an identityserver device, a request to create a data usage sponsorship campaignfrom a sponsor server device associated with a sponsor for sponsoringdata usage; receiving, by the identity server device, from the sponsorserver device, and based on providing a configuration interface,information for the data usage sponsorship campaign associated with anentity-identifiable group of users, the information for the data usagesponsorship campaign including an entity-selected first date, anentity-selected second date, entity-selected content, andentity-selected cost information; generating, by the identity serverdevice and based on the request, configuration information for the datausage sponsorship campaign; configuring, by the identity server device,the data usage sponsorship campaign based on the configurationinformation; receiving, by the identity server device and from a contentserver device, an identifier associated with a user device, theidentifier being provided to the identity server device based onembedded code included in particular content accessed by the userdevice, the embedded code being provided by the identity server deviceto the content server device, the embedded code enabling the contentserver device to support the data usage sponsorship campaign, theembedded code including one of an application, a code snippet, a script,or a widget that is embedded in the particular content, and the embeddedcode causing the user device to provide the identifier to the contentserver device; receiving, by the identity server device, informationassociated with data usage by the user device while the particularcontent is accessed by the user device; determining, by the identityserver device, whether the data usage is sponsored by the sponsor basedon the identifier and the information associated with the data usage,the sponsor sponsoring data usage associated with the particular contentaccessed by the user device on a first date, the sponsor not sponsoringdata usage associated with the particular content accessed by the userdevice on a second date, the second date being different than the firstdate, the sponsor sponsoring data usage associated with the particularcontent accessed by the user device during a first time of day, and thesponsor not sponsoring data usage associated with the particular contentaccessed by the user device during a second time of day, the second timeof day being different than the first time of day; and assigning, by theidentity server device, charges for the data usage: to an accountassociated with the user device when the data usage is not sponsored bythe sponsor, or to an account associated with the sponsor when the datausage is sponsored by the sponsor.
 2. The method of claim 1, furthercomprising: determining, by the identity server device, the sponsorbased on the identifier and the information associated with the datausage; and identifying, by the identity server device, the accountassociated with the sponsor.
 3. The method of claim 1, where theinformation associated with the data usage includes one or more of:information associated with a geographic location of the user deviceduring the data usage, or information associated with the particularcontent accessed by the user device during the data usage.
 4. The methodof claim 1, where the sponsor sponsors the data usage of the user devicebased on one or more of: a geographic location of the user device duringthe data usage, the particular content accessed by the user deviceduring the data usage, or a threshold associated with the data usage. 5.The method of claim 1, further comprising: storing, by the identityserver device, the configuration information for the data usagesponsorship campaign.
 6. The method of claim 1, where the user device isassociated with the data usage sponsorship campaign based on theidentifier.
 7. The method of claim 1, further comprising: storing theconfiguration information for the data usage sponsorship campaign.
 8. Anidentity server device comprising: one or more processors to: receive,from a sponsor server device associated with a sponsor for sponsoringdata usage, a request to create a data usage sponsorship campaign,provide, based on receiving the request, a configuration interface,receive, from the sponsor server device and based on providing theconfiguration interface, information for the data usage sponsorshipcampaign associated with an entity-identifiable group of users, theinformation for the data usage sponsorship campaign including anentity-selected first date, an entity-selected second date,entity-selected content, and entity-selected cost information, generate,based on the request, configuration information for the data usagesponsorship campaign, configure the data usage sponsorship campaignbased on the configuration information, the data usage sponsorshipcampaign sponsoring data usage associated with particular contentaccessed by a plurality of user devices on a first date; the data usagesponsorship campaign not sponsoring data usage associated with theparticular content accessed by the plurality of user devices on a seconddate, the second date being different than the first date, the datausage sponsorship campaign sponsoring data usage associated with theparticular content accessed by the plurality of user devices during afirst time of day, and the data usage sponsorship campaign notsponsoring data usage associated with the particular content accessed bythe plurality of user devices during a second time of day, the secondtime of day being different than the first time of day; receive anidentifier associated with a user device, of the plurality of userdevices, from a content server device, the identifier being provided tothe identity server device based on embedded code included in theparticular content accessed by the user device, the embedded code beingprovided by the identity server device to the content server device, theembedded code enabling the content server device to support the datausage sponsorship campaign, the embedded code including one of anapplication, a code snippet, a script, or a widget that is embedded inthe particular content, and the embedded code causing the user device toprovide the identifier to the content server device, receive informationassociated with data usage by the user device while the particularcontent is accessed by the user device, determine whether the data usageis included in the data usage sponsorship campaign based on theidentifier and the information associated with the data usage, determinethe sponsor based on the identifier and the information associated withthe data usage, identify an account associated with the sponsor, andassign charges for the data usage: to an account associated with theuser device when the data usage is not included in the data usagesponsorship campaign, or to the account associated with the sponsor whenthe data usage is included in the data usage sponsorship campaign. 9.The identity server device of claim 8, where the one or more processorsare further to: store the configuration information for the data usagesponsorship campaign.
 10. The identity server device of claim 8, wherethe information associated with the data usage includes one or more of:information associated with a geographic location of the user deviceduring the data usage, or information associated with the particularcontent accessed by the user device during the data usage.
 11. Theidentity server device of claim 8, where the data usage sponsorshipcampaign sponsors data usage associated with on one or more of: aparticular geographic location, or a particular data threshold.
 12. Theidentity server device of claim 8, where the data usage sponsorshipcampaign sponsors data usage by one or more user devices, of theplurality of user devices, associated with the sponsor.
 13. The identityserver device of claim 8, where the one or more processors are furtherto: assign a portion of the charges for the data usage to the accountassociated with the user device; and assign a remaining portion of thecharges for the data usage to the account associated with the sponsor.14. The identity server device of claim 8, where the one or moreprocessors are further to: assign a portion of the charges for the datausage to the account associated with the sponsor when the data usage issponsored by the sponsor.
 15. A non-transitory computer-readable mediumfor storing instructions, the instructions comprising: one or moreinstructions that, when executed by one or more processors of anidentity server device, cause the one or more processors to: receive,from a sponsor server device associated with a sponsor for sponsoringdata usage, a request to create a data usage sponsorship campaign;receive, from the sponsor server device and based on providing aconfiguration interface, information for a data usage sponsorshipcampaign associated with an entity-identifiable group of users, theinformation for the data usage sponsorship campaign including anentity-selected first date, an entity-selected second date,entity-selected content, and entity-selected cost information; generate,based on the request, configuration information for the data usagesponsorship campaign; configure the data usage sponsorship campaignbased on the configuration information; store the configurationinformation for the data usage sponsorship campaign; receive, from acontent server device, an identifier associated with a user device, theidentifier being provided to the identity server device based onembedded code included in particular content accessed by the userdevice, the user device being associated with the data usage sponsorshipcampaign based on the identifier, the embedded code being provided bythe identity server device to the content server device, the embeddedcode enabling the content server device to support the data usagesponsorship campaign, the embedded code including one of an application,a code snippet, a script, or a widget that is embedded in the particularcontent, and the embedded code causing the user device to provide theidentifier to the content server device, receive information associatedwith data usage by the user device while the particular content isaccessed by the user device, determine whether the data usage issponsored by the sponsor based on the identifier and the informationassociated with the data usage, the sponsor sponsoring data usageassociated with the particular content accessed by the user device on afirst date, the sponsor not sponsoring data usage associated with theparticular content accessed by the user device on a second date, thesecond date being different than the first date, the sponsor sponsoringdata usage associated with the particular content accessed by the userdevice during a first time of day, and the sponsor not sponsoring datausage associated with the particular content accessed by the user deviceduring a second time of day, the second time of day being different thanthe first time of day, and assign charges for the data usage: to anaccount associated with the user device when the data usage is notsponsored by the sponsor, or to an account associated with the sponsorwhen the data usage is sponsored by the sponsor.
 16. Thecomputer-readable medium of claim 15, where the instructions furthercomprise: one or more instructions that, when executed by the one ormore processors, cause the one or more processors to: determine thesponsor based on the identifier and the information associated with thedata usage, and identify the account associated with the sponsor. 17.The computer-readable medium of claim 15, where the informationassociated with the data usage includes one or more of: informationassociated with a geographic location of the user device during the datausage, or information associated with the particular content accessed bythe user device during the data usage.
 18. The computer-readable mediumof claim 15, where the sponsor sponsors the data usage of the userdevice based on one or more of: a geographic location of the user deviceduring the data usage, the particular content accessed by the userdevice during the data usage, or a threshold associated with the datausage.
 19. The computer-readable medium of claim 15, where theinstructions further comprise: one or more instructions that, whenexecuted by the one or more processors, cause the one or more processorsto: assign a portion of the charges for the data usage to the accountassociated with the user device; and assign a remaining portion of thecharges for the data usage to the account associated with the sponsor.20. The computer-readable medium of claim 15, where the instructionsfurther comprise: one or more instructions that, when executed by theone or more processors, cause the one or more processors to: assign aportion of the charges for the data usage to the account associated withthe sponsor when the data usage is sponsored by the sponsor.